When you design your FAP files, consider any alternative designs which will make the system process more efficiently. For instance, if you design a form with a large number of small overlapping boxes, it will take longer to process than one designed with longer, and more efficient continuous lines.
Also, isolate objects which cause the FAP file to be in-lined into their own FAP files. Avoid including other objects with the object that causes the FAP file to be in-lined. For instance, if you must use the TextMergeParagraph rule in a text area, avoid including other objects in that text area. Especially avoid mixing bar code, rotated variables, or charts with text areas.
Charts, especially 3D charts, look great and can add a lot to your form, but remember that they have a big affect on performance. Charts are one kind of inline graphics which include dynamic data. This means the GenData program has to perform computations on them and charts cannot be pre-compiled for the GenPrint program.
If you use charts,
Make the chart as simple as possible and limit the number of series. The more complicated the chart, the more data in the NA file, and the larger the data stream from the GenPrint program. It takes a long time to print a large data stream.
Avoid putting several charts on a single section.
Avoid mixing charts with other objects on the same section.
If you are using a Xerox Metacode printer, make sure you are using a CompressMode option other than UNC (uncompressed). You’ll find this option in the PrtType:XER control group.
Loading times are affected by the number, size, and complexity of your section files. If you can combine some sections in the same form, do so unless they are conditional sections. A lot of small floating sections on one page, will slow performance.
© Copyright 2018, Oracle and/or its affiliates. All rights reserved. Legal notices.